Thanks for putting this together! Not an easy document to write, so it needs a bit more polishing.

I have submitted a thorough editing pass with PR #1183. Please take a look at this first. After reviewing my updates, please rename the file to moving-to-casper.md to remove any ambiguity with the word “migrate”.

In addition, I have a few more requests.

Please try to remove repeated explanations in the five categories you defined (lifecycle, storage, methods etc.). For example, we are referencing Named Keys and Dictionaries three times. Resources are defined twice.

State management can be combined with storage, actually. If you want to keep them separate, try to find another way to organize the content so there is less duplication.

I would like to see more links to coding examples. There are some, but many sections seem theoretical. You could link to any relevant topics (either in the Casper docs or externally).
For example, when explaining get_key, at a minimum, link to docs.rs. Also, point to the reading-and-writing-to-the-blockchain.md file.
This request applies to all concepts and explanations introduced.

Finally, a little more structure would be needed. For example, what are the comparison points in each tab? Are they covered for each blockchain?

Please also check the Casper docs style guidelines before submitting a PR. It's not in this PR's checklist, but it's not optional.

Thanks for the updates, @KMCreatesWorlds.
Here are a few minor edit requests. From the previous feedback, I see the following have been addressed - thanks!

• Renamed file to moving-to-casper.md
• Combined state management with storage
• Removed repeated definitions (Resouces, Named Keys, Dictionaries)

Let's discuss the following on the live call:

• Cross-links to each topic in the Casper docs or link out to coding examples
• Tab structure. What are the comparison points in each tab? Are they covered for each blockchain?

cc @ACStoneCL

I ran this locally and it looks great. Thank you, @KMCreatesWorlds!